Microsoft Client for DOS, or MSClient. file sources: basic client backdoor server user interface ************************************************** This setup will let you look at disks and directories on Windows 95. 98, NT, etc. computers from your DOS based CNC machine tool. Computers running as DOS servers can be accessed as well. File sharing and permissions must be set on the other computers in order for the machine tool to see the files. Since the machine tool acts only as a client, you will not be able to access it from other computers or see it in the Network Neighborhood. There is a backdoor method of making your machine tool into a server so that it can be seen and accessed by other computers. This description follows the basic client setup. ----------------------------------------------------------------------------------- Networking DOS computers as clients using MS Client. Some versions of DOS work better than others. I prefer DOS 7.0 that is the basis of Windows 95 4.00.950 or Windows 95 4.00.950a. DOS 6.xx works well too. DOS 7.0 from Windows 95 4.00.950b (OSR2) and up will not let you upgrade to a server configuration since Microsoft chose not to support the SHARE in these later versions. The MS client is available at . The file names are dsk3-1.exe and dsk3-2.exe. Get the readme file as well. Here's the step-by-step; 1) Execute the dsk3 files in a temporary directory to unpack them. There are some duplications in the dsk3-2.exe file. Hit Y to allow the previous files to be overridden. 2) Type SETUP and press enter 3) Press enter to accept "setup network client" 4) Press enter to accept "c:\net" as install directory, (wait for software to examine system) 5) Press enter "to setup for best performance" 6) Type user name (a name you would like to identify your machine tool with) and press enter 7) Arrow up to "change setup options" and press enter 8) Arrow up to "change redirector options" and press enter 9) Arrow up to "use basic redirector" and press enter 10) Press enter to accept "the listed options are correct" 11) Arrow up to "change network configuration" and press enter 12) Arrow up to "add protocol" and press enter 13) Arrow down to "microsoft NetBEUI" and press enter 14) Press the tab key to highlight the top menu 15) Arrow down to "NWLink IPX compatible transport" (don't press enter!) 16) Press the tab key to highlight the lower menu 17) Arrow up to "remove" and press enter 18) Press enter to accept "network configuration is correct" 19) Press enter to accept "the listed options are correct" (wait for software to copy files to your system) 20) Press F3 to "quit setup without restarting your computer" NOTE: Because there is a glitch in the setup program, it cannot place the proper address for your network interface card in the protocol.ini file. The following edits are required to set this properly. you will need to know the I/O base address and IRQ line used by your network card. 21) Change to the c:\net directory 22) edit the protocol.ini file 23) Change the line "IOBASE=0x300" to reflect the I/O base address of your network interface card. For example; "IOBASE=0x2C0" 24) Change the line "INTERUPT=3" to reflect the IRQ line used by your network interface card. For example; "INTERRUPT=10" 25) Save the protocol.ini file 26) Reboot your system 27) When the system has rebooted, Press enter to accept the user name you previously established. 28) Press enter or type a password if you wish to use one. 29) Press Y when prompted for a password list file. 30) Confirm your password or press enter if you don't have one. 31) Type NET and enter. This should bring up the disk connections screen. 32) Enter a computer and drive letter on your network (ie;\\roscoe\c) and see if you can connect. If it shows up in the "current connections" box, you have succeeded. That's all there is to it! The client has assigned the next available drive letter to the new network path. In the CNC controller load (file) menu, change the directory to this new drive and it'll be looking at the other computer's disk. ---------------------------------------------------------------------------------- ----------------------------------------------------------------------- Adding peer to peer server capabilities to your CNC system. Remember, this will not work with the DOS version supplied with W95 OSR2 You have already installed and configured the client from the files dsk3-1.exe and dsk3-2.exe. When configuring the client, make sure you install the Microsoft NetBEUI protocol. Also make sure you have the proper INT and ADDY set for your NIC. I've been running the Novell/Anthem NE2000 driver on all my machines since most of my NICs are second hand salvages that I don't have any software for. Make sure the client is working properly by making a connection to a shared resource on another Win95 machine. Type "net" and the user interface will pop up. Type in the resource on the highlighted line. For example, \\roscoe\c would give you access to the "C" drive on the machine named "roscoe" as long as the c drive was enabled for sharing on "roscoe". Next you need to execute the file wg1049.exe in your \net directory. Let it over-write whatever it wants. This gives the DOS machine server capabilities. Make the changes in the system.ini and autoexec.bat that we had discused before. Remember, every time you run setup.exe, the system.ini gets changed back to the =off default. This the price you pay for the free client/server hack... Execute the file netshar.exe in the same directory. This installs the user interface to configure shared resources on the DOS machine. To share resources, just type "netshare" and you can configure your machine to share any of it's resources. Now you should be able to see the machines in the Network Neighborhood. All the NNhood functions work just like a regular WIN95 P2P server. The one exception is you cannot check the properties of the DOS server disk or do remote administration with the basic redirector running. If you want to experiment, you can maximize conventional memory and try using the full redirector. Some machines can stuff the code into umb quite effectively if you fool around with the autoexec and config files enough. Here's what needs to be in the config.sys and autoexec.bat, and system.ini for the peer to peer server to work: *********************autoexec.bat**************** PATH c:\;C:\NET;C:\WINDOWS;C:\WINDOWS\COMMAND loadhigh share C:\NET\net start /yes loadhigh c:\net\net start server /yes loadhigh command.com rem I didn't loadhigh the "net start" command just cause this machine makes rem better use of umb with other code. Your milage may vary... ****************config.sys**************** FILES=40 buffers=50 LASTDRIVE=Z device=c:\windows\himem.sys device=c:\windows\emm386.exe noems dos=high,umb devicehigh=C:\NET\ifshlp.sys ******************system.ini****************** [network] filesharing=yes printsharing=yes autologon=yes computername=ROSCOE lanroot=C:\NET username=roscoe workgroup=PRIMARY reconnect=yes dospophotkey=N lmlogon=0 logondomain=PRIMARY preferredredir=basic autostart=basic maxconnections=8 [network drivers] netcard=ne2000.dos transport=ndishlp.sys,*netbeui devdir=C:\NET LoadRMDrivers=yes [Password Lists] *Shares=C:\NET\Shares.PWL ROSCOE=C:\NET\ROSCOE.PWL